Overview

This application allows the user to maintain parameters on a system-wide level, and also define application-specific overrides.

Parameter Naming Conventions

A parameter name consists of a Section and an Entry.  Sections are high level groupings which make searching for parameters easier.  Usually these will relate to the functional area of the system where the parameter is being used, such as "ArenaRostering" or "System".  The Entry field specifies the parameter name, such as "SessionTimeout".  Parameter names are usually written in Pascal case.

Creating New Parameters

While the Maintain Parameters application allows the creation of new parameters, there are some fields that need to be set up correctly to allow the parameter value to be validated correctly.  Developers should review the documentation on the adm_Parameters table to learn about these extra fields which aren't visible from the Maintain Parameters table.

Application Specific Overrides

Some parameters may be overridden on an application-level basis.  If this is allowed for the selected parameter, a grid will be visible on the Maintain Warehouse Parameters application where the user will be able to add Application Names and specific values.  Application specific overrides are stored in the adm_Application_Parameters table, while system-wide parameter values are stored in the adm_Parameters table.

Additional Information

The Maintain Parameters application contains the following fields:

Field	Description
Section	The section grouping for this parameter (see Maintain Warehouse Parameters above).
Entry	The parameter name.
Value	The system-wide setting for the parameter.  This value is restricted depending on the validation settings when the parameter was created by the developer.
Description	A human readable description which explains the purpose of the parameter.

See Also

• ret_DataWarehouse.adm_Parameters table
• ret_DataWarehouse.adm_Application_Parameters table